home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
The 640 MEG Shareware Studio 2
/
The 640 Meg Shareware Studio CD-ROM Volume II (Data Express)(1993).ISO
/
wc3x
/
szwcbats.zip
/
READ.ME
next >
Wrap
Text File
|
1992-11-04
|
5KB
|
88 lines
********************************************************************************
SuperZmodem Batch Files for use with Wildcat 3.55S
********************************************************************************
November 4, 1992
Thanks to Ron Lotterman for finding an error in the read.me file dated
October 14, 1992. I hope this has not cause any inconvenience. It
concerned the definitions of the following two files which has now been
corrected: (The batch files remain the same and unchanged.)
FILES: SZUP.BAT (used to SEND FROM WILDCAT! TO A REMOTE USER - SEND)
SZDOWN.BAT (used to RECEIVE TO YOUR WILDCAT! BBS - RECEIVE)
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
First, READ THE SZMODEM.DOC file entirely! It will help you when reading
the information below. Also please consider registering your copy of
SZMODEM with Scott Baker.
I found SuperZmodem to be great for it's additional features and set out
to get it to run with my Wildcat BBS. This has only been tested on
Wildcat v3.55S!
These are the current batch files I am using for SuperZmodem as an external
protocol on Wildcat 3.55S. I'll be the first to admit that I'm rather new
at configuring external protocols but found that SuperZmodem had so many
benefits that it was worth the time and effort to find something that worked
with Wildcat.
These files may be adapted for multi-line use, I'm sure. (If you run
a multi-line system...you're probably smart enough to know how to configure
it anyway and WAY ahead of me! :)
I have tested these batch files extensively and they seem to be running
fine, however you should know that you are at your own risk.
I have elected NOT to use the parameter SET DSZLOG=STATUS.LOG in my
autoexec.bat for a couple of reasons. It was causing problems with SuperZmodem
during an aborted upload TO Wildcat. If the SET command is in the
autoexec.bat, it will cause SuperZmodem to automatically envoke a DSZ type
log in the current directory, which in Wildcat's case is \WC30\WCWORK\NODE1\EP.
To make a long story short, Wildcat sees the DSZ.LOG (renamed to STATUS.LOG)
and thinks that it was an uploaded file and adds it to the database. This,
of course, is not acceptable.
On the other hand, it IS necessary for Wildcat to see a DSZ.LOG when you
are DOWNLOADING from it to see if a file transfer was successful or not.
To get around this, I have added the command line parameter /DL to the
"SZ" command line. (SZUP.BAT) This will cause a DSZ type log to be
written after the download is complete for Wildcat to read to determine
status. The batch file renames DSZLOG to STATUS.LOG as the Wildcat
Manual states.
SuperZmodem also had another peculiarity with Wildcat. If an upload to
a Wildcat board was aborted, the portion of the file transferred prior
to the "abort" was added to the Wildcat database and not flagged as
an aborted upload and deleted. To make up for this, I added another
line to the batch file to rename and delete files that weren't complete
so when Wildcat looked for the uploaded files, it wouldn't find any
and therefore see the upload as "aborted" or unsuccessful. This will
only happen when SuperZmodem exits with an errorlevel 1. Unfortunately,
if someone is batch uploading and the abort happens on the 2nd or 3rd
file transfer, all files in that session will be deleted. I couldn't
think of a way to totally fix this problem. SuperZmodem exits normally
with an errorlevel 0.
When configuring SZMODEM with SZCONFIG.EXE, I have (under paths) put
C:\WC30 as my SZMODEM path. This is so SuperZmodem will write the
SZMODEM.LOG to the \WC30 directory instead of the external protocol
directory where it might be mistaken for an uploaded file by Wildcat.
I also DISABLED the DSZ.LOG in SZCONFIG.EXE. Again, this will prevent
the DSZLOG from being written to the EP directory when uploading TO
the Wildcat board. We manually envoke the DSZ.LOG with the /DL
parameter as stated before in the "SZ" (SZUP.BAT) batch file.
These batch files were written using the standard Wildcat filenames
and structures. If you are using different filenames or structures
for these directories, you will have to rename some of the file names
and paths to match your setup. It's also a GOOD idea to enable the
CTS/RTS handshaking feature with SZCONFIG.EXE.
If anyone has found a better way of using SuperZmodem with Wildcat,
I'd appreciate hearing from you. I monitor the MSI HQ Wildcat! Echo
or you can call me at the WTUE BBS at 513-274-3231.
Tom Carroll